Overview
What is Jira Software?
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
Best-in-class project management & coordination, & planning technology
Atlassian Architect
Essential software for a project development
TrustRadius Insights
My Verdict on Jira Software : Should you use it or not!
best for tracking everything
Extremely good on workflow monitoring and handy reporting tools
Jira - The Saviour of lazy people
Streamlining Project Management with Jira: A Quick Review of its Features and Capabilities
Jira Software - Agility with the simplest and most effective #1 ALM solution
Jira Software is capable of end to end product management
Hey guys! let's have an amazing review for this software.
- Problems addressed by this software:
1. Keeping the whole team in single …
Jira - Excellent Project & Workflow management tool
Amazing project manager tool!
Jira helps me do my job better and easier!
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
Standard
$8.15
Premium
$16
Data Center
$44,000
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $81.85 per month 10 users
Product Demos
JIRA Project Management Tutorial for Beginners (2022)
The full overview: Roadmaps in Jira Software
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is Jira Software?
Jira Software is a project management tool software used by agile teams and supports any agile methodology, be it scrum, kanban, or a team's own unique flavor. From agile boards to reports, users can plan, track, and manage agile software development projects. And since not every team works the same way, Jira Software allows teams to customize workflows, permissions, and schemes to match the unique needs of each team.
Jira templates also support use cases in enterprise marketing management, and projects to support operations, design HR, and enterprise marketing management.
With Jira Software, teams are able to:
- Track versions, features, and progress at a glance
- Re-prioritize user stories and bugs
- Estimate stories, adjust sprint scope, check velocity, and re-prioritize issues
- Estimate, track and report on story points; become more accurate
- Report on agile metrics to provide real-time, actionable data on team efficiency, quality, and overall performance
- Integrate with all the tools their dev team is already using, from the rest of the Atlassian suite (Bitbucket, Bamboo, Fisheye, and Crucible) to other popular developer tools on-premise or cloud (e.g., GitHub and Jenkins).
- Provide greater flexibility to curate which teams have access to which information with sprint and project-level permissions
- Flexibly tailor Jira tasks and their workflows to a specific team's use case
- Extend Jira with over 1,800 apps from the Atlassian Marketplace to fit any capability not provided by default
Jira Software Videos
Jira Software Integrations
Jira Software Competitors
Jira Software Technical Details
Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
---|---|
Operating Systems | Windows, Mac |
Mobile Application | Apple iOS, Android |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(3244)Community Insights
- Pros
- Cons
Easy-to-use tool with minimal learning curve: Users have found JIRA to be an intuitive and user-friendly tool that requires minimal effort to learn. Several reviewers mentioned that they were able to navigate through the platform easily and quickly adapt to its features.
Seamless collaboration through integration with other tools: Many users appreciated JIRA's ability to integrate with various plugins and add-ons, enabling seamless collaboration across different teams and departments. This integration allowed for enhanced productivity by bringing together different tools into one centralized platform.
Flexibility of customization: The flexibility of JIRA in terms of customization was highly regarded by users. They mentioned being able to customize bugs, tasks, and stories based on the specific requirements of their projects. This flexibility helped them tailor JIRA to their unique project management needs.
Confusing and overwhelming user interface: Many users have expressed frustration with the confusing and overwhelming user interface of JIRA. They find it difficult to efficiently complete tasks due to a lack of intuitive navigation and cluttered design.
Complexity and difficulty in customization: A significant number of reviewers find JIRA's customization options to be complex and challenging. It often requires dedicated training to effectively navigate and utilize the software's customization features.
Limitations in reports, charts, and attachments: Users have reported challenges in sharing information within JIRA due to limitations in reports, charts, and attachments. These limitations hinder effective collaboration, communication, and data visualization.
Attribute Ratings
Reviews
(1-25 of 52)- Organization - JIRA is great for being able to organize the scope of major features or product launches in a way that can be visualized across teams.
- Communication - In a remote-first world, JIRA allows you to maintain tight communication and aligned scope even as teams work across time zones.
- Velocity Tracking/Project planning - JIRA allows teams to visualize and understand expectations for when to deliver a project, have insight into project/team/individual capacity, and track work overtime.
- Learning curve - There is a learning curve to working in JIRA, it is not immediately intuitive to a new user. It usually requires a lot of learning in order to most effectively and optimally use JIRA. A lot of it comes with time and experience.
- Lack of standardization - There are a lot of bells and whistles in JIRA. It's really great that you can label or organize tickets in a variety of different ways. It is really up to the organization to create a method of organizing within all of those bells and whistles. This means each time you go to a new organization, there is a lot of overlap, but you are learning a lot of new methods and best practices as well.
- JIRA can be a little bit frustrating and hard to use in terms of the ability to type and format content in each epic or individual story. It's good enough and JIRA has done a lot recently to add integrations (such as Figma) or other ways to link design, but it can be sometimes hard to translate complex requirements into JIRA in a consumable way.
Atlassian Architect
- agile boards
- dashboards
- Jira Query Language
- Reporting
- Atlassian Marketplace of Apps
- Community for discussions and Q&A
- notifications with link to issues
- company managed projects vs team managed projects
- allows for duplicate names of entities - can get confusing
- administrators get too many emails - they are added to the watch list for every project they work on.
Amazing project manager tool!
- Ticketing Feature
- Project Management
- Field mapping
- Flexible portal
- Software glitches - sometimes window takes a lot of time to load
- Real time updates needs to work upon
- Integration with other apps can also be worked upon
Top tool to create or modify the software features
- For creating new PRs for new features
- Convey the idea for end user
- Include nitty gritty details of the required changes
- AI based matching with already existing tickets.
- Dedicated sections for particular category
- Auto text completion, text suggestion while creating the ticket
Go Agile in the right way
- Projects progress tracking.
- Tracking teams performance.
- well defined and easy to use tool.
- friendly and highly customizable.
- Creating custom reports could be complicated for non-technical people.
- Really basic add-ons shouldn't cost.
- Query requires dev language knowledge.
We rely on Jira Software to prioritize work across multiple groups inside the Engineering team who handle different aspects of the platform. Having cross-functional visibility is key to understand and track the workload being distributed across the backend and frontend teams.
- Customizability is impressive. Being able to establish automations and custom fields of all types helps when we need to build new templates to support different efforts.
- Integration into third-party apps like Git, Bitbutcket, and Zendesk helps streamline our processes and visibility across teams.
- Easily customizable dashboards are a huge help when it comes to analyzing the vast amount of data available in Jira Software.
- Bloated - the app has so [many] features and functionality that it tends to bog down from time to time.
- Expensive - Jira Software is by far one of the most expensive offerings out there.
- No dark mode support - it's 2021, we should have [a] dark mode.
- Nickle and dime features - Need to pay for common functionality like Git integration.
- Lack of automated alerts around metrics like ticket age, last update, etc.
It would also be great if Jira Software supported automatically sending an email notification to requesters when a ticket's last updated date gets to a defined period to prevent defect and task tickets from being forgotten.
Jira - Immediate adoption by our team for backlog management
- Out-of-the-box backlog management with Kanban board
- Easy and intuitive customizing for basic requirements
- Huge community and marketplace extensions availability
- Confusing set of products to setup a full suite (Jira to Confluence to Service Desk, etc.)
- Advanced requirements call for an expert
- Moving to pure-Cloud in the near-future
Jira Software - the Swiss Army Knife of Software
- Release management
- Tagging
- Process flows
- Collaboration
- Bulk ticket processing
- Pre-built Dashboards
- Bulk ticket creation via import
- Automated reminders for stale tickets
Jira Software is a good task management solution for medium to large software teams
- Task tracking
- Notifications of new tasks and task updates
- Permission based boards and ticket updates
- Jira Software could use some UI updates for its dashboard
- Jira Software needs an archive feature for old projects
- Permission flow for users and projects is very convoluted and hard to manage
Jira Software: Best SaaS for Software Development Projects!
- Seamless Integration with development tools such as Slack, Github or Bitbucket.
- Very customizable workspace; you can choose the components of each task for your board, your own icons, labels and automated workflows.
- Relate all the issues/tasks with Epics and visualize upcomings results in Product Roadmap.
- They could improve the format of attaching files on Conduent, using pages with attachments is not the most friendly option.
- In the board by default is included to-do, doing, done on stages. It would be good to have QA (Quality Assurance) by default with some automations based on time and deployments.
- I think tasks could have 2 assignees (I know there is a possibility to add an assistant) but some issues are equal responsibility for two collaborators.
Jira for Cross-Departmental Collaboration
- Customization - you can set up your Jira instance however you would like to meet your needs.
- Streamlines communication between teams. You can add multiple users across departments with different access.
- Filter and report to view the information you need. This was important for us in locating open bug tickets submitted by Support so we could stay on top of them.
- For someone using Jira for the very first time, it is not the most intuitive system. Maybe some more in-app tooltips would be helpful for users logging in for the first few times.
Jira Software allows quick management of your software backlog with tons of features!
For internal uses, it addresses the need for a central location for all IT tickets, as well as asset management. In addition to answering simple requests from employees - all hardware assets are managed in Jira. We setup a project where the tickets are each an asset and it's worked very well. In addition, using our internal management software (custom) we setup an integration which pairs each ticket logged with that asset.
Externally, the Jira system allows us to easily interact with readers who are having issues. The solid email ticket feature was the main attraction for using Jira for this.
- Manage tickets, whether with or without SLA.
- Manage projects using agile including a backlog.
- Managing tickets for users outside the system with the service desk feature.
- Management of the software is very difficult at times, although has improved.
- Ability to manage resources is really non-existent, there are some plugins but they are ALL buggy (I've tested them all).
- Better integration with Trello, would love to see this happen. Right now it's very clumsy.
Additionally, if you wish to manage the backlog using agile Kanban - the boards are excellent and can be customized for the team needs. Even has the great ability to style and add rules to flag items. That said, I'd love to see a better integration with Trello as that system's "boards" are much better quality and easier to use. I've got teams using both and Trello is always the winner.
This system can be tailored for other uses, such as storing a "database" of sorts like assets. However, it takes some setup but can work. Where it won't work is managing resources. Say you want to manage resources to ensure you have enough developers to cover future projects - with the current plugins it's VERY difficult. The integrations are always clumsy and get out of sync and the plugins are very slow. Finally, the data it provides is basically useless. You are better off using another tool outside Jira.
- Notification of changes - I appreciate the email notification when things have been updated in the tickets.
- The visual workflow is fantastic
- This might just be the way that we use it, but the ownership updates as the ticket progress can be a little clunky.
- I am not sure why on some tickets I can reassign to the next person and on others, I have to request that the assignment gets changed.
Review Jira software
So, the organization uses the Jira software for tracking, better vis[i]bility, for agile project management, customization of the activities and generate reports to check the amount of completion and remaining amount of work.
- It is being used for Bug, Story and Task tracking, whereas it also enabled the team for recording or even finding or tracking bugs.
- These are also being used as a product/project management tool and in turn allow the user when it comes to assignment of the tasks which would require attention.
- It also provides a flexibility of having a kanban board which gives the user with a better vis[i]bility of what has been done, what is in progress and what is still remaining.
- This software is also being used as a scrum software development which is giving one the scope to be fast paced as it has a fixed and focused iteration.
- There is also a flexibility for management as well as tracking of the projects that might support both the traditional as well as agile project management and gives a centralized and customization flexibility.
- There is also a feature enabled in Jira Software for generation of reports like that of the BurnDown Chart, Sprint Chart, Velocity chart etc.
- There are still room of improvements.
- When it comes to using Jira Software in Mobile Phone as web version or as mobile version, it doesn't give a great UI / User friendly experience.
- Follows some of the complex integration as well as migration from many of the different ALM systems.
- The reports being generated are not reusable.
- The UI in the application is a little cluttered and also the filtering is not very convenient to use.
2) This is used for an agile software development and provides a single centralized view of stories or bugs or reports that needs to be generated.
3) This is also used for integrating with different systems like Confluence, Outlook, Slack, Teams etc.
4) This is also highly customizable as it allows the user to create any sort of issue where they can customize the workflow for any of the requirement, and user can also customize the timeline, reports, fields etc.
- Notifications
- Tagging Users
- Category of activity
- Attachment size
- Need to Learn Advanced Features
- Sensitive to Mistyped keys
The best task management tool for your projects
- Extensibility through custom add-ons
- Highly configurable with all its major features
- Great integration with other Atlassian products
- Many features can be too overwhelming for new users
- Being very engineering centric increases complexity to non-technical users
an Engineer's Review of Jira
- Adding a detailed description of the task
- Tagging different people for comments
- Adding pictures, documents etc.
- Often adding a picture needs several tries due to "failed" error messages
- Time tracking is very basic and can certainly improve
- The watching option does not always send an email notification with updates, even if it is set to do so
- [Prioritizing] the tasks and add them to current/ next sprint based on importance and urgency of completing it
- Documenting everything, including wireframes, scope, comments and updates in just 1 ticket rather than multiple emails/ chats etc
- Easy tracking of past events, closure, updates and where did the task end up
- Adding of additional fields (if needed) to track a few metrics is not available
- Most important things for tickets is to see what was the TAT (Turn around Time) and that doesn't come automatically
- It is easy to know the status of the work situation in the project at all times because all users in the project are informed of every event.
- Jira has an above-average quality of integration with project services, which allows it to be used in conjunction with many online storage or instant messaging services.
- Atlassian constantly sends out newsletters about updates that are released for the Jira platform, which keeps us informed at all times about new software enhancements and strategies we can apply using these new dynamics to work better.
- Jira does not include a manual configuration function for editing workflows using information modeling strategies.
- The platform tends to be slow when working with external workflows while they load.
- Jira does not integrate with Analytics tracking platforms extensive enough to be able to review our performance figures during marketing campaigns we do to the project from some other non-Atlassian software.
Jira Software in CICD
It effectively manages the development cycle and development time. Every role can use it like BAs, Testers, Developers. They know their task based on the description and acceptance criteria.
- Jira can be changed to different stages like In Review, In Development etc.
- It can effectively be used to identify hours spent on each story/Jira.
- It can be connected with Bitbucket to create branch in repository.
- It could create an extension to use applications like Outlook to send mails.
- It could add more audit-related fields to track change history.
- It is hard to tell the time spent if the same Jira have been used by more than 1 person.
Jira Only!!
- Sprint board
- Defect board
- Crate tasks, sub-tasks, spikes and epics.
- Record documents
- Better linking within stories and tasks.
- Less mandatory fields shouldn't be there.
- Too many views.
A must-have tool!
We use it for all purposes. The fields are really extensive and easy to use. Additionally, the filters are very useful and you can track the issues very easily. Filters have advance search features too which incorporate very simple query language and can fetch specific results. Jira dashboards are another feature that is used daily. You can add various gadgets to the dashboard and track the progress of the project instantly. You can also share dashboards with people where they can check the status and this, in turn, saves you time.
- Issue logging and tracking.
- Dashboards.
- You need to save the filter and basically make it public before using it in the gadget on the dashboard. If it's not public the gadget will not be displayed to any other user. This is a tedious task sometimes.
- There should some way where you can save your formats of bug logging etc. so you don't have to type the same things every time and you can just simply pre-populate the format.
JIRA - The Best ALM Tool in the Market.
1. User stories in form of project backlog
2. Acceptance criteria
3. Creating bugs
4. Analysis ticket
5. Maintaining story workflows (from ready for dev to closed)
6. Logging work hours spent on each individual ticket/story
It is also very helpful in creating a very simplistic boundary line between the on going sprint and the backlog (all my projects have been executed in Agile mode). In addition to it, as my projects have always had more than one sprint going on simultaneously and the stories part of those sprints related to each other, it acts as a very elegant tool for representing such views where the information is easy to comprehend for any developer or tester.
- Single view for all the user stories (active sprint/backlog)
- Ability to generate reports of various types for each of the active / closed sprints for e.g. burndown chart, sprint velocity etc.
- Ability to track release tickets - we can create tickets which are supposed to go for production from various sprints in one single page and manage it from there.
- Integration of communication tools like Hipchat and Slack makes it very easy for tracking & responding to notifications.
- Mobile app of JIRA is not so holistic in nature and one has to navigate a lot to do various things which are very easy to do in web application.
2. If tickets have various labels, one can view the tickets using the labels as the filter.
3. Reports are very easy to generate, they also come in form of pie charts, graphs etc.
4. A dashboard view of all the tracks going on gives a beautiful integrated view of the progress made in the current sprint.
Inappropriate - JIRA reports are not easy to reuse in the sense that the graphical reports generated are not downloadable in form of image and using other techniques leads to resolution issues for those report images.
Manage your projects with a simple and easy to use interface
- It is very simple, basic and simple to use.
- It allows precise customizable estimates according to the needs of the project.
- You can have administrative control of the company's activities (projects, processes, procedures).
- It is compatible in virtually all databases.
- It offers Web access with support for the main browsers in the market, email notifications, as well as many applications that provide additional resources to Jira.
- Although Jira is an excellent tool for project management, the cost can be somewhat expensive.
- Its initial configuration proved to be complicated.
- It can be difficult for beginners, because it is difficult to understand its characteristics.
JIRA -- The all in one cost-effective and integrated project management solution for our Organization
- Bug life cycle management.
- Grouping of deliverables as: epic, story, change request, bugs, tickets, enquiries, etc.
- Logging estimates and tracking actual efforts, giving effective variance computation.
- Computing metrics for our projects using the custom fields in JIRA.
- The SLA management is ineffective.
- The assignee has to be an individual, which is a restriction. JIRA needs to enable issue assignment to a group/department as well, to bring it to an issue dashboard.
- Query management can be made easy with some add-ons like 'Script runner' which is currently outside JIRA.